KEP-5607: Allow hostNetwork pods to use user namespaces #5608
+416
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
HirazawaUi
commented
Oct 3, 2025
HirazawaUi
commented
- One-line PR description: Allow hostNetwork pods to use user namespaces
- Issue link: Allow HostNetwork Pods to Use User Namespaces #5607
- Other comments:
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: HirazawaUi The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
kind/kep
4 tasks
16 tasks
mrunalp
reviewed
Oct 6, 2025
| When the `UserNamespacesHostNetworkSupport` feature gate is enabled, we will relax this validation check. | ||
| The kube-apiserver will accept such a Pod spec and pass it on to the kubelet. | ||
| At this point, the responsibility for successfully creating and running the Pod shifts to the container runtime. | ||
| If the low-level container runtime (e.g., containerd/runc) does not support this combination, the pod will remain stuck in the `ContainerCreating` state and report an exception event, which is the expected behavior. |
There was a problem hiding this comment.
If we go with this proposal, we should include making it work with containers/crio/runc.
mrunalp
reviewed
Oct 6, 2025
| ### User Stories (Optional) | ||
|
|
||
| #### Story 1 | ||
| As a cluster administrator, I want to enable user namespaces for my control plane static Pods (e.g., kube-apiserver, kube-controller-manager) to follow the principle of least privilege and reduce the attack surface. These Pods need to use hostNetwork to interact correctly with the cluster network. By enabling the new feature gate, I can add a critical layer of security isolation to these vital components without changing their networking model. |
There was a problem hiding this comment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.